Problems with FrameMaker or Microsoft Word

This section helps you troubleshoot issues related to ePublisher interacting with FrameMaker and Microsoft Word.

Error: Error Communicating with Adobe FrameMaker

If you install FrameMaker after installing ePublisher, the ePublisher add-ins for FrameMaker might not be installed.

To resolve this issue

  1. Make sure all FrameMaker instances are shutdown and no background instances are running.

  2. Run a 'Update/Repair' install using the ePublisher Express installer.

Error: Cannot Duplicate Document

This error will occur if you install FrameMaker or Microsoft Word after installing ePublisher, the ePublisher add-ins for Word and FrameMaker might not be installed.

To resolve this issue

  1. Make sure all FrameMaker or Word instances are shutdown and no background instances are running.

  2. Run a 'Update/Repair' install using the ePublisher Express installer.

If the generation log reports the error at step 3: Word.BeginPreProcessPhase or 3: Word.WriteBuiltInStyleNames, a Microsoft Defender attack surface reduction (ASR) rule may be blocking the ePublisher macro template wwdoc.dotm in Microsoft Word. Windows also displays an "Action blocked" notification, and ePublisher logs a warning that begins:

The ePublisher conversion macros did not run in Microsoft Word. Security policy may be blocking the macro template 'wwdoc.dotm'

Each document that could not be converted is left out of the output, the generation log reports an error that names it, and AutoMap skips deployment. Reinstalling does not help. Ask your IT team to add the per-rule exclusion for wwdoc.dotm described in the attack surface reduction section of the ePublisher Silent Installation Guide.

If the generation log reports that Microsoft Word showed a dialog, Word opened a dialog during the conversion, and nobody could answer it because ePublisher runs Word hidden. ePublisher closed Word after 30 seconds and did not convert the document. The warning names the document and the dialog:

Microsoft Word showed the dialog "<title>" while applying the project's settings to the document '<source>.docx'. ePublisher runs Word hidden, so nobody can answer the dialog; ePublisher closed Word after 30 seconds and did not convert the document.

When ePublisher can read the dialog's text, the warning ends with The dialog said: and that text. As with a blocked macro template, the document is left out of the output and AutoMap skips deployment. For the dialogs Word can show, including its security notice about fields that refer to other files, see the Word dialogs section of the ePublisher Silent Installation Guide.

The WebWorks Rasterizer Printer Is Not Available

When the WebWorks Rasterizer printer is missing, generating output from Microsoft Word or Adobe FrameMaker documents logs this warning:

The "WebWorks Rasterizer" printer is not available, so images in Microsoft Word and Adobe FrameMaker documents cannot be converted. Make sure the Print Spooler service is running, then run Rasterizer_Helper.exe from the ePublisher program folder as an administrator to install the printer.

The output is generated without the converted images. To resolve this issue, follow the steps in The WebWorks Rasterizer Printer Was Not Installed.

Last modified date: 11/05/2026